Description

Following the discussion #6961 I'd suggest to add a new asymmetric matcher expect.oneOf() for better support of optional properties, which can often be undefined or null if not set.

test('optional properties can be null or undefined', () => {
  const user = {
    id: 1,
    firstName: 'John',
    middleName: undefined,
    lastName: 'Doe'
  }

  expect(user).toEqual({
    id: expect.any(Number),
    firstName: expect.any(String),
    middleName: expect.oneOf([expect.any(String), undefined]),
    lastName: expect.any(String),
  })
})

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.